Master multi-agent orchestration using Claude Code's TeammateTool and Task system.

This guide shows you how to activate Office 2024 Professional Plus LTSC using a valid license key or the phone activation method.
Applies to both fresh installations and upgrades.

• A valid Office 2024 Pro LTSC product key
• Internet connection (for online activation) or phone (for offline)

This guide has been moved to the official KSP Modding Libs Wiki, where it is maintained. This guide will not be maintained. https://github.com/KSPModdingLibs/KSPModdingWiki/wiki/Creating-a-new-Plugin-Mod-on-Windows

I am not a mod developer, I am just starting out. I got a lot of help, and I'm writing this as a mental note for myself, as well as a hopefully correct guide for others who may want to start with KSP mod developement.

• Download Visual Studio Community (not VS Code) from here: https://visualstudio.microsoft.com/vs/community/
• Run the installer
• During installation, make sure you install .Net desktop developement as seen here:

A wrapper skill that integrates Zeno recursive codebase analysis with Clawdbot.

1. Copy this folder to ~/.clawdbot/skills/zeno/
2. Clone the main Zeno repo for runtime configs:

git clone https://github.com/anth0nylawrence/zeno.git /tmp/zeno-upstream

The order is not relevant.

⚠️ Disclaimer: This guide is provided solely for educational purposes. The creator assumes no responsibility for any damage, data loss, or other adverse effects that may occur as a result of following these instructions. Proceed entirely at your own risk!

Many users who have rooted their devices finds issues where system or third-party applications detect the root status and refuse to operate. This guide outlines a procedure to hide root detection on the majority of Android devices, specifically the ones running Noble ROM for Samsung S9/S9+/N9. The approach detailed here leverages KernelSU-Next in conjunction with SuSFS.

• Delete unused or obsolete files when your changes make them irrelevant (refactors, feature removals, etc.), and revert files only when the change is yours or explicitly requested. If a git operation leaves you unsure about other agents' in-flight work, stop and coordinate instead of deleting.
• Before attempting to delete a file to resolve a local type/lint failure, stop and ask the user. Other agents are often editing adjacent files; deleting their work to silence an error is never acceptable without explicit approval.
• NEVER edit .env or any environment variable files—only the user may change them.
• Coordinate with other agents before removing their in-progress edits—don't revert or delete work you didn't author unless everyone agrees.
• Moving/renaming and restoring files is allowed.
• ABSOLUTELY NEVER run destructive git operations (e.g., git reset --hard, rm, git checkout/git restore to an older commit) unless the user gives an explicit, written instruction in this conversation. Treat t